Add memory and CPU resource limits to containers#111
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
e8ec692 to
4632e71
Compare
lpiwowar
left a comment
There was a problem hiding this comment.
Since this is about ensuring that all pods have resource requests and limits set can you also please resolve the missing CPU limit on the PostgreSQL pod as well? 🙏
I missed it |
|
@omkarjoshi0304 I guess you want to rebase on top latest |
waiting for @umago PR to get merge |
|
@omkarjoshi0304 it has already been merged -> #112 |
The llama-stack and lightspeed-service-api containers had no resource limits, allowing unlimited memory consumption. The console plugin containers also lacked resource definitions. This adds appropriate requests and limits to prevent unbounded resource usage and protect node stability.
The PostgreSQL container was missing a CPU limit while having memory limits set. Add CPU limit of 500m to match the approach of ensuring all containers have both CPU and memory limits defined.
Done |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lpiwowar, omkarjoshi0304, umago The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
8faeaf1
into
openstack-lightspeed:lcore-migration

llama-stackcontainer(requests: 500m CPU / 2Gi memory, limits: 2 CPU / 8Gi memory)
lightspeed-service-apicontainer(requests: 250m CPU / 512Mi memory, limits: 1 CPU / 2Gi memory)
(requests: 50m CPU / 64Mi memory, limits: 200m CPU / 256Mi memory)